Skip to content

feat: modernize Python tooling (pyproject.toml + uv)#1136

Open
irfanuddinahmad wants to merge 6 commits into
masterfrom
irfanuddinahmad/uv-migration
Open

feat: modernize Python tooling (pyproject.toml + uv)#1136
irfanuddinahmad wants to merge 6 commits into
masterfrom
irfanuddinahmad/uv-migration

Conversation

@irfanuddinahmad

Copy link
Copy Markdown
Contributor

Summary

Modernizes this repo's Python tooling per the org-wide standardization tracked in openedx/public-engineering#513 (and the parent openedx/public-engineering#506):

  • Consolidate tool config into pyproject.toml, replacing setup.cfg. This is a deployed Django service, not a published package, so no [project]/packaging metadata or semantic-release is added.
  • Switch dependency management from pip-compile to uv: requirements/*.in+*.txt are replaced by PEP 735 [dependency-groups] + a single uv.lock. Since there's no [project] table, runtime deps live in an explicit base group that other groups compose via {include-group = "base"}.
  • Update the existing tox.ini/Makefile to use tox-uv's uv-venv-lock-runner, and switch mysql-migrations-check.yml to install uv and run via uv sync/uv run tox.

Heads up: this repo's ci.yml runs tests inside a prebuilt edxops/enterprise-catalog-dev Docker image (via validate.shmake requirements && make validate), built in a separate repo. That image will need uv installed before this branch's CI can pass -- I didn't have access to fix that from here.

Part of openedx/public-engineering#513.

Test plan

  • uv lock resolves cleanly (193 packages)
  • Could not fully verify uv sync/uv run tox on my machine (no libmysqlclient/pkg-config locally to build mysqlclient from source) -- CI's ubuntu-latest runners have these preinstalled, so this needs verifying there, along with the Docker image update noted above.

🤖 Generated with Claude Code

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Jul 9, 2026
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @openedx/2u-enterprise.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jul 9, 2026
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Ready for Review in Contributions Jul 13, 2026
@mphilbrick211 mphilbrick211 requested a review from a team July 13, 2026 15:52
Irfan Ahmad and others added 6 commits July 15, 2026 09:10
Move isort/pytest settings from setup.cfg into pyproject.toml.
enterprise-catalog is a deployed Django service, not a published package,
so no [build-system]/packaging metadata is added here. The [flake8]
section in setup.cfg is dropped since flake8 isn't invoked anywhere in
this repo (Makefile/tox.ini/CI); pycodestyle config moves to tox.ini in
the next commit alongside the dependency-groups migration.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replace requirements/*.in + *.txt with PEP 735 dependency-groups in
pyproject.toml and a single uv.lock. Since this repo has no [project]
packaging metadata, runtime deps live in an explicit `base` group that
test/quality/doc/production/dev all compose via {include-group = "base"}.
A dedicated `ci` group holds tox/tox-uv, composed into `dev`. Update the
existing tox.ini to use the uv-venv-lock-runner, update the Makefile, and
switch the MySQL8 migrations-check workflow to install uv and run
`uv sync`/`uv run`.

The main Django CI workflow (ci.yml) runs tests inside the
`edxops/enterprise-catalog-dev` devstack image via validate.sh -> `make
requirements && make validate`; since that image is built in a separate
repo, it isn't touched here, but it will need `uv` preinstalled before
this workflow will pass again. Also dropped requirements/optional.txt
and requirements/monitoring/, which were unused by any Makefile target
or workflow, and the pip<25.3 constraint, which was a pip-tools/pip
build-compatibility pin with no bearing under uv.

Note: could not fully verify `uv sync`/`uv run tox` locally on this
machine (no libmysqlclient/pkg-config for building mysqlclient from
source) -- `uv lock` resolves cleanly; full sync needs verifying via CI.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
CI runs this script inside the edxops/enterprise-catalog-dev Docker image,
which doesn't have uv preinstalled -- "make: uv: No such file or directory".
Installing it here unblocks CI without needing to update that image
separately, though updating the image directly (so this doesn't need to
pip install uv on every run) would still be worth doing separately.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…t dirs

pylint scans the whole enterprise_catalog tree, which includes per-app
tests/ subdirectories that import ddt/pytest -- caught proactively after
finding the same gap in license-manager's quality group (CI failure
there: "Unable to import 'ddt'"). Compose {include-group = "test"}
instead of just "base".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
quality already gets edx-lint transitively via {include-group = "test"},
which lists it directly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Every uv sync/uv run invocation in this repo names an explicit --group,
but uv's implicit default group (named "dev") was still being synced
alongside it, silently pulling the entire dev/test/quality/ci superset
into every target. Verified with `uv sync --group ci`.

Also adds .venv to .gitignore alongside the existing venv/ entry.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@irfanuddinahmad irfanuddinahmad force-pushed the irfanuddinahmad/uv-migration branch from 70602cd to 64f835f Compare July 15, 2026 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Ready for Review

Development

Successfully merging this pull request may close these issues.

3 participants